Goal Oriented Requirements Engineering for Non-functional Factors

Goal-Oriented Requirements Engineering

We review some of the history of Software Engineering since 1968 and discuss some the underlying concepts of Structured and ObjectOriented Software Development, noting that they don't offer means of capturing and analyzing design spaces for the software-to-be. We then introduce Goal-Oriented Requirements Engineering concepts adopted from the KAOS and i* modelling frameworks, noting key ideas. W...

Goal-Oriented Requirements Engineering: A Guided Tour

Goals capture, at different levels of abstraction, the various objectives the system under consideration should achieve. Goal-oriented requirements engineering is concerned with the use of goals for eliciting, elaborating, structuring, specifying, analyzing, negotiating, documenting, and modifying requirements. This area has received increasing attention over the past few years. The paper revie...

Handling Obstacles in Goal-Oriented Requirements Engineering

ÐRequirements engineering is concerned with the elicitation of high-level goals to be achieved by the envisioned system, the refinement of such goals and their operationalization into specifications of services and constraints and the assignment of responsibilities for the resulting requirements to agents such as humans, devices, and software. Requirements engineering processes often result in ...

Extending Argumentation to Goal-Oriented Requirements Engineering

A key goal in safety-critical system development is to provide assurance that the critical requirements are sufficiently addressed. This goal is typically refined into three sub-goals, namely that the safety requirements are validated, satisfied and traceable. The achievement of these sub-goals is typically communicated by means of a safety argument supported by items of evidence (e.g. testing,...

Goal-Oriented Approaches to Requirements Engineering